Remote provisioning of telephone channel unit using inband digital code sequences transmitted over tandem link

ABSTRACT

To remotely interrogate a telecommunications services channel unit resident in any office along a tandem network communication link, a control link establishment code sequence comprised of one or more sets of predefined digital code bytes is transmitted from a test system controller. The format of the control link establishment sequence is such that as it is forwarded down the link, any tandem channel unit or units that are intermediate the test system controller and the destination channel unit will transition to a transparent state, so that only the destination channel unit will be able transition to an interrogation, response mode. During the command-response mode, channel units connected in tandem between the selected channel unit and the interrogating test system controller continue to assume a transparent state, so that command and response messages propagate unmodified through such intermediate channel units. A command message may contain information for defining the operational configuration of the selected channel unit. It may be used to read the operational configuration or status of the selected channel unit, or it may contain supervisory control information for directing the selected channel unit to conform with a prescribed operational condition.

This is a continuation of application Ser. No. 07/813,346, filed Dec.24, 1991, now U.S. Pat. No. 5,390,179, issued Feb. 14, 1995.

FIELD OF THE INVENTION

The present invention relates in general to telephone communicationsystems and is particularly directed to a mechanism for establishing avirtual control link over a tandem digital communications network (e.g.using a T1 carrier) between a supervisory control unit and a selectedchannel unit, thereby enabling the supervisory control unit to performprescribed network functionality with respect to the selected channelunit, including provisioning, status monitoring and obtaining inventoryinformation.

BACKGROUND OF THE INVENTION

Although the proliferation of digital signal processing equipment hasmet with widespread acceptance in a variety of industries, telephonecompanies have been slow to convert to or integrate digital signallingsubsystems and communication schemes into their well established copperwire networks. One of the principal reasons for such reticence is thefact that a significant part, if not all, of an established telephonenetwork employs analog signalling equipment. Consequently, to beaccepted by the telephone company, any digital product must not only bea cost effective replacement for existing circuitry, but it must besignal-compatible with any remaining analog units of the network towhich it may be interfaced.

Advantageously, the assignee of the present application currently offersto the industry digital signalling/interface units that enable digitalservices to be integrated into a variety of office environments, andallow digital signalling capability to be extended over a tandemcommunication link all the way to the customer site, without totallypreempting the conventional use of analog signalling for maintenance andtesting. Specifically, copending U.S. patent application Ser. No.686,415, filed Apr. 16, 1991, entitled "Analog Service Channel Port forDigital Interface," by R. E. Bowlin et al, and co-pending U.S. patentapplication Ser. No. 752,777, filed Aug. 30, 1991, entitled "DigitalTandem Channel Unit Interface for Telecommunications Network," by C. L.Hall, each of which is assigned to the assignee of the presentapplication and the disclosure of each of which is herein incorporated,describe respective types of digital data port or channel units thatallow the replacement of conventional analog equipment with digitaldevices that are used for signalling, voice and data communications,while still retaining the ability to be interfaced with analog (tone)signalling equipment for carrying out maintenance and test procedures.

A requirement of this and any equipment installed in the communicationnetwork link is that it be maintained in good working order and, whennecessary, be capable of being provisioned to meet changing userdemands. Typically, status/performance evaluation and provisioningfunctions have been accomplished manually by a craftsperson on-site atthe channel bank in which the equipment of interest is installed. In aneffort to remedy the problem of rapidly escalating labor costs that nowface the industry, a number of equipment suppliers have proposedreplacing existing channel bank equipment with intelligent channelsystems (smart channel banks combined with smart channel units).

One example of such a system is described in the U.S. Pat. No. 4,849,972to Hackett et al entitled "Digital Data Communications Terminal andModules Therefor." In accordance with this patented system, D4 channelbank equipment may be locally and remotely provisioned by way of anattendant microcontroller that is included as part of the commonequipment. Each channel unit includes its own local microprocessor andassociated NVRAM for storing provisioning data. All provisioning iseffected by way of a supervisory communication path between theattendant controller and the channel bank. There is no capability ofeffecting remote provisioning through one or more tandem orcascade-connected channel units, through which multiple offices areinterconnected with one another. In addition, the system of Hackett etal provides no mechanism for provisioning channel bank equipment from atest access location between two end offices, such as a test accesslocation provided at a cross-connected interface within a siteintermediate the end offices of the network. Consequently, as one wouldexpect, a replacement solution of the type described in the Hackett etal patent has met with considerable resistance by the telephonecompanies due to the significant increase in per channel equipment cost,which is generally attributed to the need for a dedicated on site systemcontroller (computer), enhanced channel bank common equipment, and theincorporation of resident intelligence into the channel units.

SUMMARY OF THE INVENTION

In accordance with the present invention, rather than effect a wholesalereplacement of existing equipment, including the installation of aseparate system controller within the channel bank, advantage is takenof the digital communication capabilities of the channel units describedin the above referenced patent applications. Specifically, the inventioninvolves equipping such channel units (through a modification of theircommunication-control software) with the ability to be remotelyinterrogated and provisioned through a virtual control link that isestablished over a tandem communication link through which channel unitsare connected in cascade between a test system controller at aninterrogation site and the selected channel unit, using a modified setof inband digital code sequences that are customarily employed foreffecting a latching loopback condition.

In particular, the present invention provides a technique for remotelyinterrogating a selected channel unit resident in any office along atandem network communication link, by initially transmitting onto thecommunication link what is hereinafter termed a `control linkestablishment code sequence` comprised of one or more sets of predefineddigital code bytes. This format of the control link establishmentsequence is such that as it is forwarded down the link, any tandemchannel unit or units that are connected in cascade intermediate thetest system controller and the destination channel unit will transitionto a transparent state. This communication transparency of suchintermediate units allows a control link establishment code set withinthe overall control link establishment sequence, which will enable thedestination channel unit to receive and respond to command messages fromthe test system controller, to propagate down the link to thedestination channel unit, so that only the destination channel unit willbe able to transition to an interrogation, response mode.

When the destination channel unit has acknowledged receipt of thecontrol link establishment code set, indicating that a virtualpoint-to-point, command-response control link has been establishedbetween the test system controller and the destination channel unit, thedestination channel unit transitions to a command-response mode. Duringthe command-response mode, tandem channel units, which are intermediatethe selected channel unit and the interrogating test system controller,continue to assume a transparent state, so that command and responsemessages propagate unmodified through such intermediate tandem channelunits. A command message may contain information for defining theoperational configuration of the selected channel unit. It may be usedto read the operational configuration or status of the selected channelunit, or it may contain supervisory control information for directingthe selected channel unit to conform with a prescribed operationalcondition.

As mentioned above, the control link establishment sequence is comprisedof one or more sets of digital code bytes customarily used to define alatching loopback condition of a channel unit. It also includes aprescribed code byte other than those customarily employed for defininga latching loopback condition of a channel unit. Digital code bytescustomarily employed for defining a latching loopback condition includea transition in progress (TIP) code, a loopback enable (LBE) code, aloopback select (LSC) code, a far end voice (FEV) code and an all one'scode. The present invention does not employ a loopback select code,which is device type specific, and further, it modifies the above codeset with a test alert (TA) code, hereinafter referred to as an alertdevice (ADC) code, which is neither device type specific, nor does itcorrespond to any of the codes that have been reserved as yet unassignedcodes in the telecommunications industry, so that its use will notconflict with any future assignments of control codes.

More particularly, the digital code sequence that is used to enable achannel unit to complete a (virtual) communication path or control linkwith the system controller comprises a `control link establishment` codesequence or set: TIP - ADC - LBE - FEV. In accordance with theinvention, the communication control mechanism of each channel unit thatis intended to have the capability of being remotely interrogated andprovisioned is configured such that, whenever it sees this `linkestablishment` code sequence, it transitions to the command-responsemode, so that an `active session` of exchanging messages between thetest system controller and the selected channel unit may be conducted.The selected channel unit also transmits a multiplexer (MUX) out-of-sync(MOS) code downstream to prevent any other channel units from monitoringcommand-response messages between the test system controller and theselected channel unit, so that a downstream user will know that the linkis out of service.

The code sequence that is used to cause a channel unit to transition tothe transparent mode comprises a `go transparent` code sequence or set:TIP - ADC - LBE - ALL `1`S - ADC. When a channel unit initially sees a`go transparent` code sequence, it transitions to the transparent mode.It also modifies selected ones of the `go transparent` code sequence andthen passes the modified sequence down the link. Specifically, thechannel unit passes the initial TIP and ADC codes as is, it maps the LBEcode into a device type code and converts the ALL `1`S code into a TIPcode. This converted TIP code serves as the initial code of the nextcode set (either another `go transparent` code set or the `control linkestablishment` code set. The ALL `1`S code clears existing channelformats of that channel unit. Upon receipt of the second ADC byte, theintermediate channel unit enters a transparent state in which all codemodification or mapping is turned off, so that any subsequently receivedcode bytes (which may be either part of additional `go transparent` codesets or a `link establishment` code sequence) propagate through theintermediate channel unit unmodified.

Once the selected channel unit has transitioned to an active session,command-response mode, it proceeds to exchange messages with the testsystem controller until the link is terminated from the interrogationsite. To exit from or terminate an active session, the test systemcontroller may transmit a TIP code byte. In addition, if a prescribedperiod of time expires without the channel unit receiving a commandmessage, the control link is terminated. The prescribed period of timeis sufficient to allow a craftsperson to manually interrogate, provisionthe channel unit.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 diagrammatically illustrates a simplified example of arepresentative digital carrier telephone network in which the remoteprovisioning mechanism of the present invention may be employed;

FIG. 2 diagrammatically illustrates the configuration of a DS0 data portchannel unit;

FIG. 3 is a general state diagram of the remote provisioning mechanismin accordance with the present invention;

FIG. 4 is a state diagram of the operation of a channel unit in thecourse of the execution of the remote provisioning mechanism of thepresent invention;

FIG. 5 diagrammatically shows the communication link flow of a linkestablishment control sequence and command-response messages of theremote provisioning mechanism of the present invention;

FIG. 6 shows the format of a command message sourced from a test systemcontroller; and

FIG. 7 illustrates the structure of a DS0 byte in which thecommunication protocol of the present invention is embedded.

DETAILED DESCRIPTION

Before describing in detail the remote provisioning mechanism inaccordance with the present invention, it should be observed that thepresent invention resides primarily in what is effectively a prescribedcommunication protocol and an augmentation of the control softwareemployed by the micro-controller within the digital signalling/interfaceunits detailed in the assignee's previously referenced co-pending patentapplications, so as to permit a remote test system controller toselectively establish a control link with and exchange command responsemessages with such channel units on a one at a time basis. The detailsof the circuitry of the channel units are otherwise essentiallyunaffected. Consequently, the configuration of such channel units andthe manner in which they are interfaced with other communicationequipment of the telephone network have been illustrated in the drawingsby readily understandable block diagrams, which show only those specificdetails that are pertinent to the present invention, so as not toobscure the disclosure with details which will be readily apparent tothose skilled in the art having the benefit of the description herein.Thus, the block diagram illustrations of the Figures are primarilyintended to illustrate the major components of the system in aconvenient functional grouping, whereby the present invention may bemore readily understood.

FIG. 1 diagrammatically illustrates a simplified example of arepresentative digital carrier telephone network in which the remoteprovisioning mechanism of the present invention is intended to be used.The network itself is shown as comprising a first end office 10, locatedat the `west` end of the network as viewed in the Figure, having aD4-type channel bank 11 containing an OCU data port or channel unit 12of the type described in the above referenced Bowlin et al application.OCU data port 12 interfaces bipolar signals carried by a four-wire link13, which is coupled to analog, digital communication equipment servedby the network, with an all digital communication link 14, such as a T1(1.544 Mb/s) link. T1 link 14 contains a first portion 14-1 throughwhich frames of DS1 digital data are carried between `west` end office10 and an intermediate station 30. Intermediate station 30, in turn, iscoupled via a T1 carrier link portion 14-2 to a hub office 20, locatedat the `east` end of link 14-2. Intermediate office 30 and hub office 20have D4-type channel banks containing DS0 data ports of the typedescribed in the above referenced Hall application. Intermediate office30 has a pair of cross-connected channel banks 31-32 containing DS0dataports 41, 42, while hub office 20 contains a pair of cross-connectedchannel banks 21-23 containing DS0 data ports 22-24. DS0 data port 24 ofchannel bank 23 interfaces with link 14-3 for the DS1 signal formatcarried by the T1 carrier link portion 14-3. T1 carrier link portion14-3 is shown as being connected to an end office 28, having a channelbank 27, which contains an OCU data port 29 for servicing analog,digital communication equipment at an `eastwardmost` end of the network.

As described above and as shown in FIG. 1, interposed in tandem withinT1 digital link 14, between west end office 10 and hub office 20, areone or more intermediate offices, a single intermediate office beingshown at 30, having `west` and `east` channel banks 31 and 32 coupled torespective portions of T1 digital link 14. An intra-office cross connect(typically on the order of 1500 feet of communication cable) betweenchannel banks 31 and 32 of intermediate central office 30 is formed of afour-wire transmit/receive pair 44, opposite ends of which are ported torespective `west` and `east` tandem DS0 dataports or channel units 41and 42 in the manner described in the Hall application. As describedtherein, each of digital tandem-connected DS0 dataports 41, 42 is portedto interface frames of DS1 data on T1 link 14 and corresponding framesof DS0 data of the four-wire intra-office digital T/R link 44 throughwhich the digital tandem dataport (channel unit) pair 41--42 is linkedacross the office.

As is described in the above referenced applications, each digitalchannel unit, whether it be an OCU dataport channel unit, such as unit12 resident in `west` end office 10, or a DS0 dataport channel unit,such as those resident in hub office 20 and intermediate office 30,includes respective transmit/receive buffers associated with therespective (bipolar/DS1/DS0) ports of that unit. These buffers arecontrolled by a resident micro-controller for interfacing DS1 formatteddata traffic from the line (T1 link) side of the unit, retiming thetraffic as a DS0 data stream (in the case of a DS0 data port) or abipolar data stream (in the case of an OCU data port) for transmissionfrom the channel unit, and reconverting bipolar signals (in the case ofan OCU data port) or DS0 data frames (in the case of a DS0 data port)into DS1 data frames for transmission over T1 link 14. In addition,controllably enabled loopback paths are provided between the DS1 andbipolar/DS0 ports of the channel unit, so as to permit a channelloopback either at the line side of the unit or at the drop side of theunit.

For purposes of facilitating an understanding of the present invention,the remote provisioning mechanism will be detailed with o reference to aDS0 data port channel unit, such as DS0 dataport channel unit 22 withinhub office 20 or tandem-connected DS0 dataports 41, 42 withinintermediate office 30, the details of which are set forth in the abovereferenced Hall application. It should be understood, of course, thatthe manner in which the link establishment and command/responsecommunication protocol in accordance with the present invention isembodied in the microcontroller of a DS0 dataport channel unit isequally applicable to the OCU dataport channel unit described in theBowlin application. Indeed, as described in the Hall application, thegeneral architectures of a DS0 data port and an OCU data port are verysimilar, each containing a communications control processor ormicrocontroller, which is interfaced with each of the signallingportions of the channel unit and controls the formatting andtransmissions of successive frames of data between the digital T1 linkand an associated DS0 or bipolar signalling port. It is also to beunderstood that the use of the present invention is not limited to onlythese particularly identified dataport types. They are merely given asexamples of a digital telecommunication environment in which the presentinvention may be employed. What is required of the network equipment, inwhich the present invention is to be incorporated, is that itincorporate a respective channel unit containing a supervisorycommunication control mechanism, which is configurable to respond to thesignalling sequences used by the remote provisioning mechanism.

FIG. 2 diagrammatically illustrates the configuration of a DS0 data portchannel unit detailed in the co-pending Hall application, through whicha D4-type channel bank, such as those located in intermediate centraloffice 30, may be digitally coupled with DS1 digital carrier (T1) link14 and accessed by a remotely located channel unit interrogation system,hereinafter termed a test system controller (TSC). The test systemcontroller is shown at 25 in FIG. 1 as being coupled via a test accessconnection 26 to the cross-connection between respective dataports 22and 24 of channel banks 21 and 23 of hub office 20, so that the accesslocation of test system controller (TSC) 25 is between end offices 10and 28, each containing an OCU dataport. In lieu of cross-connected DS0dataports within respective D4 channel banks, hub office 20 may containa digital cross-connect system to which T1 carrier links 14-2 and 14-3are directly ported, with TSC 25 being coupled to the digitalcross-connect system for gaining access to the T1 communication channelbetween the OCU dataports within the west and east end offices 10 and28, respectively. Also, hub office 20 may be connected via T1 carrierlinks to end offices 10 and 28 without one or more intermediate officestherebetween. In this instance, hub office 20 may containcross-connected DS0 dataports of respective channel banks to which theT1 links are ported, or its may simply contain a digital cross-connect.In the former case, the TSC 25 is connected via a test access (as at 26in FIG. 1) between the dataports, while in the latter case the TSC isconnected directly to the digital cross-connect. Also there may be oneor more intermediate offices located between hub office 20 and the eastend office 28. Again, it is to be realized that the network architectureof FIG. 1 is an example and not to be considered limitative of the useof the present invention.

As pointed out previously, since the invention resides essentially in anenhancement to the control software employed by the data port'smicro-controller, the configuration and operation of those components ofthe DS0 data port that are conventional will be described in only ageneral sense. Where more detail is desired attention may be directed tothe equipment itself and to information supplied by the manufacturer.

As shown in FIG. 2, a DS0 data port channel unit comprises a four-wiretest access interface 50, comprised of tip (T) and ring (R) input andoutput port pairs 51, 52 and 53, 54 to which respective tip and ring(T,R) lines 61, 62 and tip and ring (T1,R1) lines 63, 64 of four wirecross connect link 44 are coupled. Test access to the transmitted andreceived signals of interface 50 is effected by way of bantam jackslocated on the channel unit faceplate using a DDS portable test unit(e.g. KS-20908/20909 or functional equivalent). The channel unitfaceplate also includes a conventional set of manual provisioningswitches 68 the settings of which are selectable to predefined positionsand read by the channel unit's microcontroller 80 for setting theoperation or provisioning the channel unit. As an adjunct to this switchbank, in accordance with the present invention, the channel unitfaceplate also includes a remote provisioning indicator 55 which iscoupled as an auxiliary I/O (LED) element with the channel unit'smicrocontroller 80 for providing a visual indication that the channelunit is currently subjected to a remote provisioning operation.Associated with remote provisioning indicator 55 is an alternateprovisioning (momentary) switch 57 which is also coupled as an auxiliaryI/O element used by the craftsperson to override a previouslyestablished remote provisioning of the channel unit and manuallyconfigure the channel unit through front panel switches 68. The I/Ocontrol software within the microcontroller is such that remoteprovisioning indicator 55 is illuminated continuously when the channelunit is operating in response to remote provisioning, and is off whenoperating based upon manual provisioning by way of switches 68.

Interface 50 couples respective tip and ring inputs 51, 52 through aline coupling transformer (not shown) to a bipolar receiver within a DS0receive buffer unit 71. DS0 receive buffer unit 71 comprises a bipolarreceiver, which decodes an incoming 64 Kb/s bipolar non-return to zero(NRZ) DS0 signal on the intra office cross connect 44 and buffers theconverted binary data frames for processing (retiming andretransmission) by an attendant micro-controller 80.

For this purpose, the bipolar receiver may comprise an equalizer theoutput of which is coupled to a bit slice circuit which compares theequalized signal to threshold levels that are set at one-half themagnitude of the positive and negative peaks of the bipolar data streamand outputs a dual polarity digital representation of the received dataon complementary polarity links. The data is then sampled in asynchronous sampling circuit and coupled over respective positive andnegative polarity data links to a non return-to-zero (NRZ) decoder,which outputs a binary serial data stream in accordance with thecontents of the NRZ data. The 64 KHz digital data is then coupled to acode converter which, under the control of a port micro-controller 80,provides a recovered 64 Kb/s (DS0) data stream to be retimed at the DS1data port for transmission over the T1 link as an outbound DS1 (1.544Mb/s PCM) data stream.

For outbound, DS0 data, T/R interface 50 couples respective tip and ringoutputs 53, 54 through a line coupling transformer (not shown) from abipolar transmitter within a DS0 transmit buffer unit 73. Under thecontrol of micro-controller 80, unit 73 buffers outbound frames ofbinary data DS0, which are controllably supplied to a bipolartransmitter for encoding and transmission as an outbound 64 Kb/s bipolarnon-return to zero (NRZ) DS0 signal.

Receive buffer unit 71 has its output port 75 coupled to a first port 91of a DS0 loopback interface 90, while transmit buffer unit 73 has itsinput port 77 coupled to a second port 92 of DS0 loopback interface 90.DS0 Loopback interface 90 is preferably comprised of asoftware-controlled loopback path, the throughput state of which isdefined by micro-controller 80. In its normal non-loopback condition,interface 90 couples DS0 receive port 91 to port 93 and DS0 transmitport 94 to port 92. For a DS0 or drop side loopback, the receive andtransmit communication paths through ports 91-93 and 94-92,respectively, are interrupted and a loopback path is effected throughinterface 90 from transmit port 94 to receive port 93.

Receive output port 93 of DS0 loopback interface 90 is coupled to atransmit input port 104 of a DS1 loopback interface 100. Like DS0loopback interface 90, DS1 loopback interface 100 is preferablycomprised of a software-controlled loopback path, the throughput stateof which is defined by micro-controller 80. In its normal non-loopbackcondition, DS1 loopback interface 100 couples a DS1 receive input port101 to DS1 receive output port 103 and DS1 transmit output port 102 toDS1 transmit input 104. For a DS1 or line side loopback, the receive andtransmit communication paths through ports 101-103 and 104-102,respectively, are interrupted and a loopback path is effected throughinterface 100 from transmit port 104 to receive port 103.

DS1 transmit port 102 of loopback interface 100 is coupled to a DS1transmit buffer unit 111, while its DS1 receive port 101 is coupled to aDS1 receive buffer unit 113. Transmit buffer unit 111 comprises a set ofcascaded holding registers into which a decoded DS0 data stream isloaded by DS0 bit and byte clocks in the course of transmission out overthe T1 link 14, in order to prevent byte slips resulting from phaseshifts between the 64 KHz DS0 and 1.544 MHz DS1 data clocks.

Similarly, DS1 receive buffer unit 113 comprises a set of cascadedholding registers into which an incoming PCM (T1) data stream isdownloaded by DS1 bit and byte clocks when the channel unit is enabledto receive T1 data. The receive holding registers are unloadedsynchronously by the DS0 bit and byte clocks to form the outbound DS0data stream for transmission (e.g. to a cross connected tandem channelunit within intermediate office 30).

More particularly, the contents of DS1 receive buffer unit 113 aresynchronously unloaded to a code converter, which is driven by avariable rate clock generator under the control of micro-controller 90.The code converter is also employed to controllably insert prescribedcontrol codes, such as a `loss of signal` code byte to be substitutedfor DS0 data when there is a loss of signal or a unit coupled to thechannel is asserted quiet (turned off). The 64 Kb/s data stream iscoupled to an NRZ encoder within transmit buffer 73 which encodes thedata stream into a bipolar, non return-to-zero format. The bipolar datais then output to bipolar signal line drivers. These line drivers drivethe secondary winding of the coupling transformer, which is coupled totip and ring (T1, R1) output ports 53 and 54, to which the T1 and R1lines 63, 64 of an associated signalling link interfaced to the channelbank are coupled.

As the operation of the DS0 data port of FIG. 2 is detailed in the abovereferenced Hall application, it will not be repeated here. Instead, thefollowing description will set forth the enhancement to the controlmechanism resident within micro-controller 80 and the remoteprovisioning communication protocol it employs that enables the channelunit to be interrogated by and respond to command messages issued by thetest system controller.

As described briefly above and as diagrammatically illustrated in thestate diagram of FIG. 3, the remote provisioning mechanism in accordancewith the present invention comprises two sequential events or phases.During the first phase a `control link establishment` sequence,comprised of one or more sets of predefined code bytes, is transmittedfrom the interrogating test system controller toward the selected ordestination channel unit. When properly received by the destinationchannel unit, the control link establishment code set within the controllink establishment sequence will cause the selected channel unit totransition from its IDLE MODE 301 to an ACTIVE SESSION MODE 303. Shouldthere be any intervening channel units located between the test systemcontroller and the selected channel unit, a corresponding `gotransparent` code set within the link establishment sequence will causesuch intervening channel unit to transition from its IDLE MODE 301 to aTRANSPARENT MODE 305. In this transparent mode, the channel unit iseffectively transparent to incoming communications either from anupstream source or a downstream source, so that an uninterrupted virtualcontrol link is established from, the test system controller through oneor more transparent intervening channel units to the selected channelunit. During an ensuing second `active session` phase, command messagesand response messages are exchanged between the test system controllerand the selected channel unit (ACTIVE SESSION MODE 303).

CONTROL LINK ESTABLISHMENT PHASE

The control link establishment sequence that is transmitted from the TSCduring the first phase comprises a modified sequence of inband digitalcode bytes that are customarily employed for effecting a latchingloopback condition. The individual code bytes that are used to form alink establishment sequence are shown in FIG. 4 as comprising atransition in progress (TIP) byte=S0111010, an alert device code (ADC)byte=S1101100, a loopback enable (LBE) code byte=S1010110, a far endvoice (FEV) code byte=S1011010, and an all one's (ALL `1`S) codebyte=S1111111. Within each respective code byte, S is a network framingbit (if applicable) or a don't care bit, The use of the alert devicecode (ADC) distinguishes the control link establishment sequence fromthat customarily employed for establishing a latching loopbackcondition, which employs no such ADC code.

As will be explained below, the control link establishment sequencetransmitted from the test system controller is comprised of one or moresets of the above codes, one of which contains a `control linkestablishment` set: TIP - ADC - LBE - FEV. It is the location of thisparticular set of code bytes within the overall control linkestablishment sequence that determines which channel unit along the linkis the destination or selected channel unit. Ahead of or prior to theoccurrence of the control link establishment code set within the linkestablishment sequence, one or more `go transparent` code sets aretransmitted down the link, for the purpose of placing any intermediate,channel units in a transparent mode, so as to allow the control linkestablishment code set to propagate to the destination channel unit. A`go transparent` code set consists of the code sequence: TIP - ADC -LBE - ALL `1`S - ADO.

Namely, the link establishment sequence that is transmitted from thetest system controller is comprised of one or more sets of digital codebytes each of which serves to control the state of a respective one ofchannel units that are coupled in tandem along the communications linkfrom the test system controller to the destination channel unit. Foreach intermediate channel unit located between the test systemcontroller and the selected channel unit, the link establishmentsequence is formatted to include a respective `go transparent` code set.Thus, if there are two intermediate channel units between the testsystem controller and the destination channel unit, the linkestablishment sequence will contain two `go transparent` code sets, thatare successively detected by the two intermediate channel units,followed by a `link establishment` code set, to which only thedestination channel unit responds.

FIGS. 4 and 5 respectively show a state diagram of a channel unit and,the signal flow path for establishing a virtual communication path fromthe test system controller through successive intermediate channel unitsalong the link to a selected channel unit. For purposes of the presentdescription, for the network diagram of FIG. 1, let it be assumed thattest system controller 25 desires to interrogate DS0 dataport 41 withinintermediate office 30. Interposed between dataport 41 and the testsystem controller 25 are tandem channel units 42 and 22, so thatrelative to the location of test, system controller 25 along the digitalcommunication link, DS0 dataport 41 is the third channel unit in asequence starting from the TSC coupled to hub office 20. Channel unit 22is the first channel unit and channel unit 42 is the second channelunit. Likewise, channel unit 12, which is downstream from DS0 dataport41, is channel unit number four relative to test system controller 25.

Because there are two intermediate channel units between test systemcontroller 25 and destination channel unit (DS0 dataport) 41, thecontrol link establishment sequence that must appear on the link willcontain two `go transparent` code sets (TIP - ADC - LBE - ALL `1`S -ADC), intended for channel units 22 and 42, followed by the `linkestablishment` code set (TIP - ADC - LBE - FEV) intended for channelunit (DS0 dataport) 41. To prevent erroneous detection of a code byte,each code byte is transmitted repetitively for a prescribed number ofbytes (e.g. 40 consecutive bytes) and verified by the receiving unitperforming an M-out-of-N comparison. Thus, when initiating the controllink establishment phase, the test system controller transmits aconsecutive number (40) of TIP bytes of the first `go transparent` setintended for channel unit 22.

As shown in the state diagram of FIG. 4, when a channel unit is placedin service (STATE 400), it monitors the link for the transmission of aTIP code byte sequence from the test system controller. When it hasdetected a valid TIP code byte sequence (successfully detectedM-out-of-N, e.g. 31 out of 32 TIP repeats from the TSC), the channelunit transitions to the IDLE state 401 and begins looking for the nextcode in the link establishment sequence, specifically a sequence ofconsecutive ADC bytes. Thus, in the present example, once test systemcontroller 25 has initiated the transmission of a control linkestablishment sequence by transmitting the TIP code byte, the firstchannel unit along the link which receives the TIP code (namely, channelunit 22) does not yet know whether it will be placed in a `gotransparent` mode or in a `link establishment` mode.

In accordance with the control link establishment protocol employed byeach channel unit, a TIP code is passed on down the link as is, and thechannel unit transitions to the TIP state wherein it begins looking fora valid ADC code byte sequence. Thus, as shown in FIG. 5, the channelunit 22 also forwards the TIP code byte downstream to the next channelunit (here DS0 dataport 42 Within the D4-channel bank of intermediatestation 30) and transitions to IDLE state 401. If channel unit 22 failsto verify reception of the requisite number of error free TIP codebytes, it maintains its state 400.

Upon completion of the transmission of the requisite number ofconsecutive TIP code bytes, test system controller 25 transmits the nextcode byte in the first `go transparent` set of the control linkestablishment sequence--the ADC code byte sequence. As in the case ofthe transition in progress (TIP) code byte, upon detecting a valid ADCcode byte sequence, channel unit 22 transitions from IDLE state 401 toADC state 402 and begins looking for an LBE code byte. In accordancewith the control link establishment protocol, channel unit 22 alsoforwards the ADC code byte downstream to the next channel unit, here DS0dataport 42.

Following the transmission of the ADC code byte, test system controller25 proceeds to transmit an LBE code byte sequence. When channel unit 22detects a valid LBE byte sequence (again using an M-out-of-N comparisonto validate the byte), it transitions to LBE state 403 and maps the LBEcode byte into one of a pair of map codes associated with the type ofchannel unit. For an OCU data port, the map code may be a map code suchas MAP1=S1101101; for a DS0 data port, the map code may be a map codesuch as MAP0=S0010011 when the control link is established from the dropside of the channel unit, and MAP1=S1101101 when the control link isestablished from the line side of the link. In the present example,since the test system controller 25 is located at the drop side of thelink, channel unit 22 maps the LBE code into map code MAP0=S0010011. Inaccordance with the control link establishment protocol, thistranslation or mapping of the LBE code to a prespecified map codeprevents downstream channel units from responding to the current `gotransparent` code set for the mapping channel unit 22.

In LBE state 403 channel unit 22 begins looking for the next byte to betransmitted from test system controller 25. Since channel unit 22 is anintermediate channel unit, for the first `go transparent` code settransmitted by the test system controller, the next code byte will be anALL `1`S code byte, as described above. The transmission of an ALL `1`Scode byte from the test system controller serves to clear allpreexisting channel formats in the intervening channel unit 22.

In accordance with the control link establishment protocol of thepresent invention, when a valid ALL `1`S code sequence has been receivedby a channel unit, the channel unit responds by converting the ALL `1`Scode into a TIP code and forwards the new TIP code down the link. Thisconverted TIP code serves as the first code byte of the next code setwithin the control link establishment sequence, either another `gotransparent` code set, where the next channel unit is anotherintervening channel unit, or as the first code byte of the `control linkestablishment` code set of the destination channel unit. In the presentexample, since the next downstream channel unit (DS0 dataport 42) isanother intervening channel unit, the TIP code output by channel unit 22is the TIP code of a corresponding `go transparent` code set for channelunit 42.

The test system controller next transmits an ADC byte which effectivelyserves as the terminal code byte of the first `go transparent` code set,as defined previously, and as the first ADC byte of the second `gotransparent` code set, intended for channel unit 42, of the control linkestablishment sequence. In accordance with the control linkestablishment control protocol of the present invention, channel unit 22responds to this terminating ADC code byte of the first `go transparent`code set by forwarding the ADC code byte downstream and transitioning toTRANSPARENT MODE 305 (FIG. 3). In the transparent mode, all codemodification or mapping that may be carried out by the channel unit(here channel unit 22) is turned off, so that any subsequently receivedcode bytes (which may by either part of additional `go transparent` codesets or a `link establishment` code sequence) propagate through theintermediate channel unit 22 unmodified. The ADC byte is propagateddownstream to channel unit 42 as the second byte in the `go transparent`set for channel unit 42.

Following the transmission of the ADC code byte to begin the second `gotransparent` code set of the link establishment sequence, (which clearsexisting formats of channel 22, as described above), test systemcontroller 25 transmits successive LBE and ALL `1`S code bytes of thesecond `go transparent` code set, which are propagated through (nowtransparent) channel unit 22 to downstream channel unit 42, as shown inFIG. 5. When channel unit 42 detects a valid LBE byte sequence, ittransitions to LBE state 403 and maps the LBE code byte into one of apair of map codes associated with the type of channel unit, to preventdownstream units from responding to the second `go transparent` code setfor channel unit 42. In LBE state 403 channel unit 42 begins looking forthe next valid byte sequence to be transmitted from the TSC, which, inthe present example is the ALL `1`S code byte sequence of the second `gotransparent` code set. As in case channel unit 22 for the ALL `1`S codebyte of the first `go transparent` code set, the ALL `1`S code byte ofthe second `go transparent` code byte set clears all preexisting channelformats in channel unit 42.

Channel unit 42 converts a valid sequence of ALL `1`S code bytes into asequence of TIP code bytes (which is the first code byte of the next setof code bytes of the link establishment sequence) and forwards the newTIP code byte to the next downstream channel unit. Since, in the presentexample, the next downstream channel unit 41 is the destination channelunit, the next code set contains those code bytes that define a `controllink establishment` code set. The test system controller 25 nexttransmits a sequence of ADC code bytes, which serves as the terminatingbyte of the second `go transparent` code byte set for channel unit 42,and the ADC code byte of the `control link establishment` code byte setintended for the next (destination) channel unit 41. The terminating ADCcode byte of the second `go transparent` code byte set causesintermediate channel unit 42 to enter TRANSPARENT MODE 305, so that allcode modification or mapping that may be carried out by channel unit 42is turned off, and any subsequently received code bytes propagatethrough intermediate channel unit 42 unmodified. The ADC byte ispropagated downstream to channel unit 41 as the second byte in the `linkestablishment` code byte set for channel unit 41.

Following the transmission of a sequence of the third ADC code bytes,test system controller 25 transmits a sequence of LBE code bytes of the`control link establishment` code byte set. When channel unit 41 detectsa valid LBE byte sequence, it transitions to LBE state 403 and maps theLBE code byte into one of a pair of map codes associated with the typeof channel unit. In LBE state 403 channel unit 41 begins looking for thenext valid byte to be transmitted from the TSC. Since channel unit 41 isthe destination channel unit, the next valid code byte sequence will bea sequence of FEV code bytes. Upon detecting a valid FEV code byte,destination channel 41 transitions to state 404. In this state thedestination channel unit is ready to receive command messages from thetest system controller. In accordance with the control linkestablishment protocol of the present invention, the destination channelunit loops the FEV code bytes back to the test system controller, whichallows the controller to confirm establishment of the control link. Thiscompletes the first, `control link establishment` phase of thecommunication mechanism in accordance with the present invention.

Until the control link or channel is terminated by the test systemcontroller (transmitting a TIP code) or aborted for lack of activity(e.g. a twenty minute time-out), the destination channel Unit 41 beginslooking for command messages from the test System controller during thesecond phase of operation of the link. Upon receipt of command messages,the channel unit transmits response messages back to the test systemcontroller until the link is terminated. Destination channel unit 41also transmits a multiplexer out-of-sync (MOS) code downstream toprevent any downstream units (here, channel unit 12) from monitoringcommand-response messages between the test system controller and theselected channel unit. As will be described in detail below, during thiscommand-response phase, the test system controller sends commands,followed by optional parameter data, and receives response messages fromthe selected channel unit 41, until it terminates the control link bytransmitting a TIP code or ceases transmitting command messages to thechannel unit for a prescribed length of time, in response to which thechannel unit returns to normal operation.

COMMAND-RESPONSE PHASE

COMMAND MESSAGE FORMAT

The format of a command message sourced from the test system controlleris diagrammatically illustrated in FIG. 6 as comprising a sequence ofcode bytes consisting of a start of message (SOM) field 201, a commandtype (CT) field 203, one or more optional parameter (data) code bytesthat make up a parameter field 205, and an end of message field 207.Again, as in the case of link establishment sequence code bytes, toprevent erroneous detection of a command code byte, each command codebyte is transmitted repetitively for a minimum of a prescribed number ofbytes (e.g. 40 consecutive bytes) and verified by the channel unitperforming an M-out-of-N comparison (e.g. 31 out of 32). The test systemcontroller continues to send each respective code after it hastransmitted this minimum number until the channel unit responds with acorrect next sequence bit (NSB) to be described below, or until a presettime interval has elapsed without a response (e.g. a two secondtimeout). If a valid response code is not returned from the channel unitto the TSC prior to the expiration of the timeout, the test systemcontroller begins error recovery, preferably by retransmission of thecommand message. If repeated retransmission is unsuccessful after apredetermined number retransmissions (e.g. three attempts), the testsystem controller transmits a TIP code byte to terminate the controllink. The channel unit acknowledges and responds to a valid commandmessage by sending a response message back to the test systemcontroller. If a command message contains invalid command field orparameter data, the channel unit will transmit back an error responsecode.

Each of the start of message code 201 and the end of message code 207consists of an ALL `1`S (data mode idle) code. Upon receipt of thiscode, the channel unit resynchronizes its receiver and begins lookingfor the command field (CT) code 203. Following the CT code 203 is one ormore parameter codes associated with the type of command contained inthe message. During an interrogation command message, for example, thedata within the parameter field 205 selects a specific register in thechannel unit, the contents of which are read out and placed in theparameter field of the response message. During a provisioning commandmessage, parameter field 205 contains alternating register address/databytes for loading configuration information into the channel unit'sconfiguration registers. For a supervisory command message, theparameter field is used to specify a particular operational mode to beexecuted by the channel unit.

COMMAND-RESPONSE BYTE STRUCTURE

The structure of a DS0 byte in which the communication protocol of thepresent invention is embedded is illustrated in FIG. 7. Bit 1, the mostsignificant (MSB) and first transmitted bit of the byte, is a DDSsubrate framing (SF) bit, and is treated as a don't care bit for acommand or parameter byte. The subrate framing bit is not used to allowcommand and response propagation through subrate multiplex equipment ofthe network.

The second bit, a next sequence bit (NSB), is employed to properlysequence command and data codes during message transmission. For normaltransmissions, the NSB alternates between the values 0 and 1 insuccessive code byte of a command or response frame. For this purpose,the test system controller preferably maintains a next send variablewhich is inserted as the NSB of a transmitted command frame byte. Thisone bit variable is initialized at 0 at the beginning of a commandmessage frame and is thereafter incremented modulo-two after thetransmission of each code byte. In a similar manner the channel unitmaintains a next receive variable which is inserted as the NSB of aresponse frame data byte. This one bit variable is initialized at 0 atthe beginning of a response message frame and is thereafter incrementedmodulo-two on the reception of each command frame byte. By comparing thereceived NSB with the NS in the case of the TSC, and NR value, in thecase of the channel unit, the device receiver can detect whether a codebyte is a duplicate, invalid or out of sequence.

Bits 3-7 of the byte structure of FIG. 7 contain hexadecimal commands ordata in the range of 00-1D. The value 1F obviously cannot be used, sinceit occurs in an ALL `1`S byte. The value 1E is reserved for use as anerror response from a channel unit for invalid commands and/or parameterdata. Finally, bit 8 is a DDS network control bit, used by the networkduring normal operation for control and secondary channel data. Bit 8 isalways set to the value `1` for command and response messages, in orderto minimize potential interference with the operation of other networkdevices.

EXAMPLE

TABLE 1 illustrates an example of a communication sequence between thetest system controller and a selected channel unit, beginning with thetest system controller transmitting a control link establishmentsequence (phase 1) and ending with the test system controllerterminating the control link following a successful exchange of commandand response messages during an active session (phase 2) with theselected channel unit. For purposes of simplifying the tabulation, theselected channel unit is channel unit 22 located in hub 20, relative totest system controller 25, rather than channel unit 41 identified as thedestination channel unit during the previous description, so that thelink establishment sequence will not include the transmission of any `gotransparent` code sets. For the present example, test system controller25 transmits only the control link establishment code set TIP - ADC -LBE - FEV as the control link establishment sequence. Upon receiving theterminal code byte of the control link establishment sequence--the FEVcode byte, the channel unit returns that code byte to inform the testsystem controller that the control link has been established, so thatthe test system controller may now begin transmitting command messagesto the channel unit.

Table 1 shows three respectively different command messages: 1- a `READDEVICE TYPE` message, 2- a `READ STATUS` message, and 3-a `WRITECONFIGURATION` message, which are sequentially transmitted from the testsystem controller to the channel unit and in response to which thechannel unit returns three respective response messages. The first twocommand messages (READ DEVICE TYPE, READ STATUS) are used to interrogatethe channel unit, while the third message (WRITE CONFIGURATION) is usedto remotely provision the channel unit. At the completion of the thirdmessage exchange, the test system controller terminates thecommunication path by transmitting a TIP sequence, which aborts the pathwith the selected channel unit, as described previously. The TIP code istypically repeatedly transmitted for some prescribed period of time(e.g. a minimum of two seconds).

                  TABLE 1                                                         ______________________________________                                                    TRANSMITTED   CHANNEL UNIT                                        OPERATION   TSC CODE      (CU) ACTION                                         ______________________________________                                        ESTABLISH TSC-                                                                            (40) S0111010 →                                                                      TSC sends TIPs                                      CHANNEL UNIT                                                                              (40) S1101100 →                                                                      TSC sends ADCs                                      COMMUNICA-  (120) S1010110 →                                                                     TSC sends LBEs                                      TION LINK   (40) S1011010 →                                                                      TSC sends FEVs                                                  ← S1011010                                                                             CU response FEVs                                    READ DEVICE (40) S1111111 →                                                                      TSC sends SOM                                       TYPE        ← S1111111                                                                             code to begin                                                                 command message                                                 (40) S0000001 →                                                                      TSC sends command                                                             type request.                                                   ← S1000011                                                                             Channel unit response                                                         type = DSODP                                                    (40) S1111111 →                                                                      TSC sends EOM code                                              ← S1111111                                                                             to terminate command                                                          msg.                                                READ STATUS (40) S1111111 →                                                                      TSC sends SOM to                                                ← S1111111                                                                             begin command                                                                 message                                                         (40) S0001001 →                                                                      TSC sends command                                                             type                                                            ← S1001001                                                                             CU sends response                                               (40) S10000001 →                                                                     TSC selects register 0                                          ← S00AAAA1                                                                             CU sends A=reg 0                                                              data                                                            (40) S0000101 →                                                                      TSC selects register 2                                          ← S10BBBB1                                                                             CU sends B=reg 2                                                              data                                                            (40) S1111111 →                                                                      TSC sends EOM                                                   ← S1111111                                                                             CU response DMI                                     WRITE       (40) S1111111 →                                                                      TSC sends SOM to                                    CONFIGURA-  ← S1111111                                                                             begin command                                       TION                      message                                                         (40) S0010001 →                                                                      TSC sends command                                                             type                                                            ← S1010001                                                                             CU sends response                                               (40) S1000001 →                                                                      TSC selects                                                                   configuration                                                   ← S0000001                                                                             register 0 for write                                            (40) S00DDDD1 →                                                                      TSC sends write                                                               data=D                                                          ← S10DDDD1                                                                             CU saves data and                                                             sends response.                                                 (40) S1111111 →                                                                      TSC sends EOM                                                   ← S1111111                                                                             CU response DMI                                     TSC-CHANNEL (40) S0111010 →                                                                      TSC sends TIPs                                      UNIT PATH                 CU returns to normal                                                          operation.                                          ______________________________________                                    

Set forth below is a set of illustrative examples of the specific bytestructures of commands (including those set forth in Table 1), that maybe employed for interrogating and provisioning channel units in therespective OCU data port and DS0 data port equipment described in theabove referenced co-pending patent applications. It is to be observed,however, that the various codes and definitions presented here are notlimited to these particular definitions, but may be tailored to conformwith the particular types of channel units distributed throughout thenetwork.

TSC COMMANDS

The command types (C4-C0) are binary encoded in the DS0 byte structurein bits 3-7.

    ______________________________________                                        DSO BYTE BITS:                                                                              1     2      3   4    5   6   7    8                            ______________________________________                                        COMMAND TYPE: S     NSB    C4  C3   C2  C1  C0   1                            ______________________________________                                    

The following table lists various types of commands that may be employedin accordance with the present invention. Definitions of each commandare set forth below, and its associated response.

    ______________________________________                                        COMMAND              CODE: (C4-C0)                                            ______________________________________                                        READ DEVICE TYPE     00000                                                    READ PART NUMBER     00001                                                    READ REVISION NUMBER 00010                                                    READ SERIAL NUMBER   00011                                                    READ CLEI CODE       00100                                                    READ STATUS          00101                                                    SUPERVISORY CONTROL  00110                                                    READ CONFIGURATION   00111                                                    WRITE CONFIGURATION  01000                                                    ERROR RESPONSE CODE (1E)                                                                           11110                                                    ______________________________________                                    

In the code byte descriptions, the following bit definitions apply:

bit 1, S=Network DDS Subrate Framing bit.

bit 2, NS=Next-Send sequence bit.

NR=Next-Receive sequence bit expected.

    ______________________________________                                        bits:   1      2       3    4    5    6    7    8                             ______________________________________                                        READ DEVICE TYPE                                                              command:                                                                              S      NS      0    0    0    0    0    1                             response:                                                                             S      NR      T1   T2   T3   T4   T5   1                             where:  T1-T5 (00-1D) define the type of channel unit, such                           as an OCU data port or a DSO data port referenced                             above.                                                                        For example,                                                          00000      CU OCU-DP                                                          00001      CU DSO-DP                                                          READ PART NUMBER                                                              command:                                                                              S      NS      0    0    0    0    1    1                             response:                                                                             S      NR      0    0    0    0    1    1                             select: S      NS      S1   S2   S3   S4   S5   1                             response:                                                                             S      NR      0    R1   R3   R3   R4   1                             ______________________________________                                    

where:

bits S1-S5 (00-1D) select the nibble of a hexadecimal encoded ASCIIcharacter: bits R1-R4 are reported in the response message

The part number response field is terminated with a "null" character (00hexadecimal) to signify end of character string.

    ______________________________________                                        S1-S5        R1-R4                                                            ______________________________________                                        00000        Part number, digit 1, (high nibble)                              00001        Part number, digit 1, (low nibble)                               .                                                                             .                                                                             11010        Part number, digit N, (high nibble)                              11011        Part number, digit N, (low nibble)                               11100        0000, "null" character                                           11101        0000                                                             ______________________________________                                        READ REVISION NUMBER                                                          bits:    1      2       3    4    5    6    7    8                            ______________________________________                                        command: S      NS      0    0    0    1    0    1                            response:                                                                              S      NR      0    0    0    1    0    1                            select:  S      NS      0    0    S1   S2   S3   1                            response:                                                                              S      NR      0    R1   R2   R3   R4   1                            ______________________________________                                    

where:

bits S1-S3 (00-07) select the nibble of a hexadecimal encoded ASCIIcharacter, bits R1-R4 are reported in the response message.

The revision number response field is terminated with a "null" character(00 hexadecimal) to signify end of a character string.

    ______________________________________                                        S1-S3      R1-R4                                                              ______________________________________                                        000        Revision number, digit 1, (high nibble)                            001        Revision number, digit 1, (low nibble)                             .                                                                             .                                                                             100        Revision number, digit N, (high nibble)                            101        Revision number, digit N, (low nibble)                             110        0000, "null" character                                             111        0000                                                               ______________________________________                                        READ SERIAL NUMBER                                                            bits:    1      2       3    4    5    6    7    8                            ______________________________________                                        command: S      NS      0    0    0    1    1    1                            response:                                                                              S      NR      0    0    0    1    1    1                            select:  S      NS      S1   S2   S3   S4   S5   1                            response:                                                                              S      NR      0    R1   R2   R3   R4   1                            ______________________________________                                    

where:

bits S1-S5 (00-1D) select the nibble of a hexadecimal encoded ASCIIcharacter; bits R1-R4 are reported in the response message.

    ______________________________________                                        S1-S5       R1-R4                                                             ______________________________________                                        00000       Serial number, digit 1, (high nibble)                             00001       Serial number, digit 2, (low nibble)                              .                                                                             .                                                                             11010       Serial number, digit N, (high nibble)                             11011       serial number, digit N, (low nibble)                              11100       0000, "null" character                                            11101       0000                                                              ______________________________________                                        READ CLEI CODE                                                                bits:    1      2       3    4    5    6    7    8                            ______________________________________                                        command: S      NS      0    0    1    0    0    1                            response:                                                                              S      NR      0    0    1    0    0    1                            select:  S      NS      S1   S2   S3   S4   S5   1                            response:                                                                              S      NR      0    c1   c2   c3   c4   1                            ______________________________________                                    

where:

bits S1-S4 select one of CLEI ASCII character nibbles (0-19) to be sentby the selected channel unit in bits c1-c4 of its response message.

    ______________________________________                                        S1-S5      c1-c4                                                              ______________________________________                                        00000      CLEI number, character 1, (high nibble)                            00001      CLEI number, character 1, (low nibble)                             .                                                                             .                                                                             10010      CLEI number, character 10, (high nibble)                           10011      CLEI number, character 10, (low nibble)                            10100      0000, "null" character"                                            10101      0000                                                               ______________________________________                                        SUPERVISORY CONTROL                                                           bits:    1      2       3    4    5    6    7    8                            ______________________________________                                        command: S      NS      0    0    1    1    0    1                            response:                                                                              S      NR      0    0    1    1    0    1                            control: S      NS      C1   C2   C3   C4   C5   1                            response:                                                                              S      NR      C1   C2   C3   C4   C5   1                            ______________________________________                                    

where:

C1-C5 (00-1D) are encoded supervisory commands.

CLEAR NEW DEVICE STATE (C1-C5=00000)

Resets the "New Device State" status bit to (0=off).

CLEAR STATUS REPORT (C1-C5=00001)

Performs a clear function on device status bits reported in response toa READ STATUS command message.

SELF-DIAGNOSTICS TEST (C1-C5=00010)

Requests the selected channel unit to perform a self-diagnostics test.Self-diagnostics test results are available with READ STATUS command.

RESET DEVICE (C1-C5=00011)

The RESET DEVICE command requests the selected channel unit to perform alogical reset operation. The reset operation will result in the channelunit executing a sequence equivalent to a power-up reset. Preferably theselected channel unit is configured to perform the reset operation aftera (0.5 second) delay, to allow the TSC to receive the response from thechannel unit for command acknowledgment. After a delay, the TSC sends a"terminate control" sequence to insure other channel units in thenetwork return to normal operation.

    ______________________________________                                        READ STATUS                                                                   bits:   1      2       3    4    5    6    7    8                             ______________________________________                                        command:                                                                              S      NS      0    0    1    0    1    1                             response:                                                                             S      NR      0    0    1    0    1    1                             select: S      NS      S1   S2   S3   S4   S5   1                             response:                                                                             S      NR      0    D1   D2   D3   D4   1                             ______________________________________                                    

where:

bits S1-S5 (00-1D) select a status nibble to be sent by the selectedchannel unit in data bits D1-D4, of its response message. Respectivestatus registers that may be employed in each of the above-referencedOCU data port and DS0 data port type channel units and their associatedfunctions are set forth below. It should be noted that the statusregisters listed and the information contained within these registers isnot limited to the specific register functions and code values listed,but may be augmented or modified to meet particular device typerequirements.

    __________________________________________________________________________    OCU-DP STATUS REGISTERS                                                       __________________________________________________________________________    STATUS REGISTER (S1-S5: 00000) - OPERATION                                    D1-0      spare                                                               D2-SDP    Self-Diagnostics Passed (1=on)                                      D3-SDF    Self-Diagnostics Failed (1=on)                                      D4-NDS    New Device State (1=on)                                             STATUS REGISTER (S1-S5: 00001) - ALARMS                                       D1-EPF    Non-volatile Memory Failure (1=on)                                  D2-CFGI   Configuration Invalid (1=invalid)                                   D3-0      spare                                                               D4-0      spare                                                               STATUS REGISTER (S1-S5: 00010) - PERFORMANCE MONITOR                          D1-TOF    T1 Out of Frame (1=RNDIS LOW, 0=RNDIS HIGH)                         D2-LSC    Loop Sealing Current (1=active)                                     D3-LRS    Loop Receive Signal (1=active)                                      D4-CRT    Customer Remote Test Code Event (1=on)                              CRT Code Event bit is set upon detection of Local Loop Code                   (*010X0V) from customer. The detection criteria require                       consecutive codes greater than prescribed maximum count or                    time period.                                                                  STATUS REGISTER (S1-S5: 00011) - PERFORMANCE MONITOR                          D1-0      spare                                                               D2-0      spare                                                               D3-0      spare                                                               D4-IDL    Idle Loop Circuit (1=idle, 0=active)                                STATUS REGISTER (S1-S5:1 00100) - PERFORMANCE MONITOR                         D1-RL7    Receive Signal Loss db, upper nibble (RL7-RL4)                      D2-RL6                                                                        D3-RL5                                                                        D4-RL4                                                                        STATUS REGISTER (S1-S5: 00101) - PERFORMANCE MONITOR                          D1-RL3    Receive Signal Loss db, lower nibble (RL3-RL0)                      D2-RL2                                                                        D3-RL1                                                                        D4-RL0                                                                        __________________________________________________________________________

The Receive Signal Loss is a binary encoded value with the format:

For RL7=0: Loss in db=value (RL6-RL0).

For RL7=1: Loss in db>value (RL6-RL0).

This encoding format allows the channel unit to report its value basedupon its measurement capability.

    ______________________________________                                        STATUS REGISTER (S1-S5: 00110) -                                              BIPOLAR VIOLATION ERRORS                                                      D1-BV7         (HIGH NIBBLE COUNT)                                            D2-BV6                                                                        D3-BV5                                                                        D4-BV4                                                                        STATUS REGISTER (S1-S5: 00111) -                                              BIPOLAR VIOLATION ERRORS                                                      D1-BV3         (LOW NIBBLE COUNT)                                             D2-BV2                                                                        D3-BV1                                                                        D4-BV0                                                                        ______________________________________                                    

Bipolar Violation Error Count is the total number of Bipolar ViolationCode errors since the last CLEAR STATUS REPORT command. (The countfreezes at "FF" until cleared.)

    ______________________________________                                        STATUS REGISTER (S1-S5: 01000) -                                              T1 00F COUNT (HIGH NIBBLE)                                                    D1-TC7                                                                        D2-TC6                                                                        D3-TC5                                                                        D4-TC4                                                                        STATUS REGISTER (S1-S5: 01001) -                                              T1 OOF COUNT (LOW NIBBLE)                                                     D1-TC3                                                                        D2-TC2                                                                        D3-TC1                                                                        D4-TC0                                                                        ______________________________________                                    

T1 Out-Of-Frame COUNT is the total number of detected RNDIS LOW eventssince a CLEAR STATUS REPORT command was last received. (The counterfreezes at count "FF" until cleared.)

    __________________________________________________________________________    DSO-DP STATUS REGISTERS                                                       __________________________________________________________________________    STATUS REGISTERS (S1-S5: 00000) - OPERATION                                   D1-0          spare                                                           D2-SDP        Self-Diagnostics Passed (1=on)                                  D3-SDF        Self-Diagnostics Failed (1=on)                                  D4-NDS        New Device (1=on)                                               STATUS REGISTER (S1-S5: 00001) - ALARMS                                       D1-EPF        Non-volatile Memory Failure (1=on)                              D2-CFGI       Configuration Invalid (1=invalid)                               D3-0          spare                                                           D4-0          spare                                                           STATUS REGISTER (S1-S5: 00010) - PERFORMANCE MONITOR                          D1-0          spare                                                           D2-0          spare                                                           D3-TOF        T1 Out of Frame (1=RNDIS LOW, 0=RNDIS HIGH)                     D4-AZD        All-Zeros Detected on Drop Size (1=on)                          AZD is "latched" status bit set when an all zero condition is                 detected on the Drop Side DSO channel.                                        STATUS REGISTER S1-S5: 00011) - PERFORMANCE MONITOR                           D1-0          spare                                                           D2-0          spare                                                           D3-0          spare                                                           D4-0          spare                                                           STATUS REGISTER (S1-S5: 00100) - T1 OOF COUNT (HIGH NIBBLE)                   D1-TC7                                                                        D2-TC6                                                                        D3-TC5                                                                        D4-TC4                                                                        STATUS REGISTER (S1-S5: 00101) - T1 OOF COUNT (LOW NIBBLE)                    D1-TC3                                                                        D2-TC2                                                                        D3-TC1                                                                        D4-TC0                                                                        __________________________________________________________________________

T1 Out-of-Frame COUNT is the total number of detected RNDIS LOW eventssince a CLEAR STATUS REPORT command was last received. (The counterfreezes at count "FF" until cleared.)

DEVICE PROVISIONING

Provisioning commands provide remote control and monitor of a channelunit's network operational state following its power-up sequence.Typically, each type of channel unit will have different configurationoptions and requirements. This device-dependent information is organizedin a configuration region of memory within the channel unit'smicro-controller and accessible with READ CONFIGURATION and WRITECONFIGURATION commands.

    ______________________________________                                        READ CONFIGURATION                                                            bits:       1      2      3   4   5    6    7    8                            ______________________________________                                        command:    S      NS     0   0   1    1    1    1                            response:   S      NR     0   0   1    1    1    1                            select:     S      NS     S1  S2  S3   S4   S5   1                            response:   S      NR     0   D1  D2   D3   D4   1                            ______________________________________                                    

where:

bits S1-S5 (00-1D) select the configuration nibble to be returned in aresponse message from the channel unit. The selected configurationnibble is contained in bits D1-D4 of the response message.

    ______________________________________                                        WRITE CONFIGURATION (PROVISION DEVICE)                                        bits:       1      2      3   4   5    6    7    8                            ______________________________________                                        command:    S      NS     0   1   0    0    0    1                            response:   S      NR     0   1   0    0    0    1                            select:     S      NS     S1  S2  S3   S4   S5   1                            response:   S      NR     S1  S2  S3   S4   S5   1                            data:       S      NS     0   D1  D2   D3   D4   1                            response:   S      NR     0   D1  D2   D3   D4   1                            ______________________________________                                    

where:

bits S1-S5 (00-1D) select the provision register to be written with theconfiguration information contained in the following data code, bitsD1-D4.

The provision register data, D1-D4 is stored by the channel unit innon-volatile memory.

Respective provision registers that may be employed in theabove-referenced OCU-data port and DS0 data port channel units, andtheir associated functions are set forth below. Also, as in the case ofthe status register definition set forth above, the provision registerslisted and the information contained within these provision registers isnot limited to the specific register functions and code values listed,but may be augmented or modified to meet particular device typerequirements.

    __________________________________________________________________________    OCU-DP PROVISION REGISTERS                                                    __________________________________________________________________________    PROVISION REGISTER (S1-S5: 00000) - STATE                                     D1-00S   Out-Of-Service (1=00S, 0=INS)                                        D2-RPV   Configuration (1=REMOTE, 0=LOCAL switch options)                     D3-0     spare                                                                D4-ENH   Enhanced SWITCHED 56 (1=on)                                          PROVISION REGISTER (S1-S5: 00001) - MODE                                      D1-CRT   Customer Remote Test (1=on)                                          D2-CSU   Customer Service Unit (1=on)                                         D3-B1    BANK SELECTION (B1,B0)                                               D4-B0    00 - D4 BANK                                                                  01 - SLC I/III                                                                10 - SLC II                                                          PROVISION REGISTER (S1-S5: 00010) - RATE                                      D1-EC    Error Correction (1=on)                                              D2-R2    RATE (R2,R1,R0)                                                      D3-R1    000 - 2.4 kbps                                                                          100 - 38.4 kbps                                            D4-R0    001 - 4.8 kbps                                                                          101 - 56 kbps                                                       010 - 9.6 kbps                                                                          110 - Switch 56 kbps                                                011 - 19.2 kbps                                                                         111 - 64 kbps                                              PROVISION REGISTER (S1-S5: 00011) - OPTIONS                                   D1-ETR   Extended Range Option (1=on)                                         D2-SC    Secondary Channel (1=on)                                             D3-ZS    Zero Suppression (1=on)                                              D4-LL    Latching Loopback Enable (1=on)                                      __________________________________________________________________________    DSO-DP PROVISION REGISTERS                                                    __________________________________________________________________________    PROVISION REGISTER (S1-S5: 00000) - STATE                                     D1-00S   Out-Of-Service (1=00S, 0=INS)                                        D2-RPV   Configuration (1=REMOTE, 0=LOCAL switch options)                     D3-0     spare                                                                D4-0     spare                                                                PROVISION REGISTER (S1-S5: 00001) - MODE                                      D1-0     spare                                                                D2-0     spare                                                                D3-B1    BANK SELECTION (B1,B0)                                               D4-B0    00 - D4 BANK                                                                  01 - SLC I/III                                                                10 - SLC II                                                          PROVISION REGISTER (S1-S5: 00010) - RATE                                      D1-EC    Error correction (1=on)                                              D2-R2    RATE (R2,R1,R0)                                                      D3-R1    000 - subrate                                                                           100 - 38.4 kbps                                            D4-R0    001 - spare                                                                             101 - 56 kbps                                                       010 - spare                                                                             110 - Switch 56 kbps                                                011 - 19.2 kbps                                                                         111 - 64 kbps                                              PROVISION REGISTER (S1-S5: 00011) - OPTIONS                                   D1-0     spare                                                                D2-0     spare                                                                D3-ZS    Zero Suppression (1=on)                                              D4-LL    Latching Loopback Enable (1=on)                                      __________________________________________________________________________

As will be appreciated from the foregoing description, the presentinvention, rather than effecting a wholesale replacement of existingequipment within the channel bank, takes advantage of the digitalcommunication capabilities of the channel units described in the abovereferenced patent applications, by equipping such channel units with theability to be remotely interrogated and provisioned through a virtualcontrol link that is established over a tandem communication pathbetween a test system controller at an interrogation site and theselected channel unit, using a modified set of inband digital codesequences that are customarily employed for effecting a latchingloopback condition. The format of the control link establishmentsequence is such that, as it is forwarded down the link, any channelunit or units that are intermediate the test system controller and thedestination channel unit will transition to a transparent state. Thiscommunication transparency of such intermediate units will allow acontrol link establishment code set within the overall control linkestablishment sequence to propagate down the link to the destinationchannel unit, so that only the destination channel unit will be abletransition to an interrogation, response mode. During thecommand-response mode, channel units intermediate the selected channelunit and the interrogating test system controller continue to assume atransparent state, so that command and response messages propagateunmodified through such intermediate channel units. A command messagemay contain information for defining the operational configuration ofthe selected channel unit. It may be used to read the operationalconfiguration or status of the selected channel unit, or it may containsupervisory control information for directing the selected channel unitto conform with a prescribed operational condition.

While we have shown and described an embodiment in accordance with thepresent invention, it is to be understood that the same is not limitedthereto but is susceptible to numerous changes and modifications asknown to a person skilled in the art, and we therefore do not wish to belimited to the details shown and described herein but intend to coverall such changes and modifications as are obvious to one of ordinaryskill in the art.

What is claimed:
 1. A communication method comprising the steps of:(a)transmitting a communication link establishment sequence of respectivelydifferent in-band digital code bytes, from a first device at a firstsite, over a digital communications link, along which a plurality ofsecond devices are sequentially distributed in tandem at a plurality ofsecond sites served by said digital communications link, said sequencebeing defined so as to identify a selected one of said plurality ofsecond devices; (b) in response to said sequence of respectivelydifferent in-band digital code bytes, transmitted in step (a) from saidfirst device having identified said selected one of said plurality ofsecond devices, causing said selected one of said plurality of seconddevices to establish a communication link with said first device at saidfirst site; and (c) having established said communication link betweensaid selected one of said plurality of second devices and said firstdevice in step (b), transmitting a digital message from said firstdevice at said first site over said established communication link tosaid selected second device, the contents of said digital message beingexclusive of any of said in-band digital code bytes and being effectiveto cause said selected second device to perform a prescribed task which,upon being completed, will cause said first device to have knowledge ofthe operational configuration of said selected second device.
 2. Amethod according to claim 1, wherein step (c) comprises transmitting adigital message which is effective to interrogate said selected seconddevice.
 3. A method according to claim 1, wherein step (c) comprisestransmitting a digital message which is effective to provision saidselected second device with one or more prescribed operationalparameters.
 4. A method according to claim 1, wherein step (c) comprisestransmitting a digital message which is effective to specify aprescribed operational mode to be executed by said selected seconddevice.
 5. A method according to claim 1, wherein one of saidrespectively different in-band digital code bytes is a bit pattern thatis suppressed in normal digital communications.
 6. A method according toclaim 1, wherein a first of said respectively different in-band digitalcode bytes corresponds to a transition in progress bit pattern thatcauses a respective second device receiving said transition in progressbit pattern to transition to an idle state, in which the receivingsecond device is awaiting a second of said respectively differentin-band digital code bytes to be transmitted thereto.
 7. A methodaccording to claim 6, wherein said second of said respectively differentin-band digital code bytes corresponds to an alert device bit patternthat causes a second device receiving said alert device bit pattern totransition from said idle state to an alert device state, in which thereceiving second device is awaiting transmission of a third of saidrespectively different in-band digital code bytes.
 8. A method accordingto claim 7, wherein said third of said respectively different in-banddigital code bytes corresponds to a loopback enable bit pattern that issuppressed in normal digital communications.
 9. A method according toclaim 7, wherein a fourth of said respectively different in-band digitalcode bytes corresponds to a far end voice bit pattern that causes asecond device receiving said far end voice bit pattern to transition toa state in which the receiving second device is ready to receive acommand message from said first device.
 10. A method according to claim7, wherein a fourth of said respectively different in-band digital codebytes corresponds to a far end voice bit pattern that causes a seconddevice receiving said far end voice bit pattern to loop said fourth ofsaid respectively different in-band digital code bytes back to saidfirst device to confirm establishment of an in-band communications linkbetween said receiving second device and said first device.
 11. A methodaccording to claim 1, further including the step of (d) providing anindication at said selected second device that said first device hastransmitted a digital message in step (c) which is effective toestablish a parameter of said selected second device.
 12. A methodaccording to claim 3, further including the step of (d) providing anindication at said selected second device that said first device hastransmitted a digital message in step (c) which is effective toprovision said selected second device.
 13. An arrangement for conductingdigital communications between a first device located at a first siteand a selected one of a plurality of second devices sequentiallydistributed in tandem at a plurality of second sites along a digitalcommunications link, comprising:a digital communications transmittercontained in said first device, and being operative to transmit acommunication link establishment sequence of respectively differentin-band digital code bytes over said digital communications link, saidsequence being defined so as to identify a selected one of saidplurality of second devices; a plurality of respective digitalcommunications receivers contained in respective ones of said pluralityof second device, each respective receiver being operative to monitorsaid digital communications link for said sequence of in-band digitalcode bytes and, in response to receipt of said sequence of respectivelydifferent in-band digital code bytes transmitted from said transmitterin said first device, establishing a communication link with said firstdevice at said first site; and wherein said transmitter at said firstdevice is operative, in response to the respective receiver of saidselected one of said second devices having established saidcommunication link with said first device, to transmit a digital messageover said established communication link to said selected second device,the contents of said digital message being exclusive of any of saidin-band digital code bytes and being defined so as to cause saidselected second device to perform a prescribed task which, upon beingcompleted, will cause said first device to have knowledge of theoperational configuration of said selected second device.
 14. Anarrangement according to claim 13, wherein the contents of said digitalmessage are effective to interrogate said selected second device.
 15. Anarrangement according to claim 13, wherein the contents of said digitalmessage are effective to provision said selected second device with oneor more prescribed operational parameters.
 16. An arrangement accordingto claim 13, wherein the contents of said digital message are effectiveto specify a prescribed operational mode to be executed by said selectedsecond device.
 17. An arrangement according to claim 13, wherein one ofsaid respectively different in-band digital code bytes is a bit patternthat is suppressed in normal digital communications.
 18. An arrangementaccording to claim 13, wherein a first of said respectively differentin-band digital code bytes corresponds to a transition in progress bitpattern, that causes a respective second device receiving saidtransition in progress bit pattern to transition to an idle state, inwhich the receiving second device is awaiting a second of saidrespectively different in-band digital code bytes to be transmittedthereto.
 19. An arrangement according to claim 18, wherein said secondof said respectively different in-band digital code bytes corresponds toan alert device bit pattern that causes a second device receiving saidalert device bit pattern to transition from said idle state to an alertdevice state, in which the receiving second device is awaitingtransmission of a third of said respectively different in-band digitalcode bytes.
 20. An arrangement according to claim 19, wherein said thirdof said respectively different in-band digital code bytes corresponds toa loopback enable bit pattern that is suppressed in normal digitalcommunications.
 21. An arrangement according to claim 20, wherein afourth of said respectively different in-band digital code bytescorresponds to a far end voice bit pattern, that causes a second devicereceiving said far end voice bit pattern to transition to a state inwhich the receiving second device is ready to receive a command messagefrom said first device.
 22. An arrangement according to claim 20,wherein a fourth of said respectively different in-band digital codebytes corresponds to a far end voice bit pattern that causes a seconddevice receiving said far end voice bit pattern to loop said fourth ofsaid respectively different in-band digital code bytes back to saidfirst device to confirm establishment of an in-band communications linkbetween said receiving second device and said first device.
 23. Anarrangement according to claim 13, wherein the receiver at said selectedsecond device is operative to cause said second device to provide anindication that a digital message has been transmitted thereto from saidfirst device, which digital message is effective to establish aparameter of said selected second device.
 24. An arrangement accordingto claim 13, wherein the receiver at said selected second device isoperative to cause said second device to provide an indication that adigital message has been transmitted thereto, which digital message iseffective to provision said selected second device.
 25. A method ofconducting communications between an access device located at a firstsite and a selected one of plurality of channel units sequentiallydistributed in tandem at a plurality of second sites along a digitalcommunications link, each channel unit being capable of being remotelyprovisioned by said access device at said first site, and providingperformance information, in response to being interrogated from saidaccess device at said first site, comprising the steps of:(a)transmitting, from said access device over said communication link tochannel units distributed therealong, a communication link establishmentsequence that is comprised of respectively different in-band digitalcode bytes which are effective to identify a selected one of saidplurality of channel units; (b) in response to said sequence ofrespectively different in-band digital code bytes transmitted from saidaccess device in step (a) having identified said selected one of saidplurality of channel units, causing said selected one of said pluralityof channel units to establish a communication link with said accessdevice at said first site; and (c) having established said communicationlink between said selected one of said plurality of channel units andsaid access device in step (b), conducting a command and responsedigital message exchange between said access device and said selectedchannel unit over said established communication link between accessdevice and said selected channel unit, said command and response digitalmessage exchange including a command message exclusive of any of saidin-band digital code bytes and being effective to cause selected channelunit to perform a prescribed task that, upon being completed, willprovide a response message to said access device representative of theoperational configuration of said selected channel unit.
 26. A methodaccording to claim 25, wherein step (c) comprises transmitting a digitalcommand message which is effective to interrogate said selected channelunit to derive status information therefrom in said response message.27. A method according to claim 25, wherein step (c) comprisestransmitting a digital command message which is effective to interrogatesaid selected channel unit to access performance information therefromin said response message.
 28. A method according to claim 25, whereinstep (c) comprises transmitting a digital command message which iseffective to provision said selected channel unit with one or moreprescribed operational parameters.
 29. A method according to claim 25,wherein step (c) comprises transmitting a digital command message whichis effective to specify a prescribed operational mode to be executed bysaid selected channel unit.
 30. A method according to claim 25, whereinone of said respectively different in-band digital code bytes is a bitpattern that is suppressed in normal digital communications.
 31. Amethod according to claim 25, wherein a first of said respectivelydifferent in-band digital code bytes corresponds to a transition inprogress bit pattern that causes a respective channel unit receivingsaid transition in progress bit pattern to transition to an idle state,in which the receiving channel unit is awaiting a second of saidrespectively different in-band digital code bytes to be transmittedthereto.
 32. A method according to claim 31, wherein said second of saidrespectively different in-band digital code bytes corresponds to analert device bit pattern that causes a channel unit receiving said alertdevice bit pattern to transition from said idle state to an alert devicestate, in which the receiving channel unit is awaiting transmission of athird of said respectively different in-band digital code bytes.
 33. Amethod according to claim 32, wherein said third of said respectivelydifferent in-band digital code bytes corresponds to a loopback enablebit pattern that is suppressed in normal digital communications.
 34. Amethod according to claim 32, wherein a fourth of said respectivelydifferent in-band digital code bytes corresponds to a far end voice bitpattern that causes a channel unit receiving said far end voice bitpattern to transition to a state in which the receiving channel unit isready to receive a command message from said access device.
 35. A methodaccording to claim 32, wherein a fourth of said respectively differentin-band digital code bytes corresponds to a far end voice bit patternthat causes a channel unit receiving said far end voice bit pattern toloop said fourth of said respectively different in-band digital codebytes back to said access device to confirm establishment of an in-bandcommunications link between said receiving channel unit and said accessdevice.
 36. A method according to claim 25, further including the stepof (d) providing an indication at said selected channel unit that saidaccess device transmitted a digital command message in step (c) which iseffective to establish a parameter of said selected channel unit.
 37. Amethod according to claim 25, further including the step of (d)providing an indication at said selected channel unit that said accessdevice has transmitted a digital command message in step (c) which iseffective to provision said selected channel unit.